Skip to content

chore: Update helm.md#2149

Closed
mfreeman451 wants to merge 1 commit intoscylladb:masterfrom
mfreeman451:patch-1
Closed

chore: Update helm.md#2149
mfreeman451 wants to merge 1 commit intoscylladb:masterfrom
mfreeman451:patch-1

Conversation

@mfreeman451
Copy link
Copy Markdown

@mfreeman451 mfreeman451 commented Oct 11, 2024

✏️ typo fix

Description of your changes:

Which issue is resolved by this Pull Request:
Resolves #

@mfreeman451
chore: Update helm.md
6415e32 
✏️ typo fix
@scylla-operator-bot scylla-operator-bot Bot added do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Oct 11, 2024
@scylla-operator-bot
Copy link
Copy Markdown
Contributor

scylla-operator-bot Bot commented Oct 11, 2024

Hi @mfreeman451. Thanks for your PR.

I'm waiting for a scylladb member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@scylla-operator-bot scylla-operator-bot Bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 11, 2024
@scylla-operator-bot
Copy link
Copy Markdown
Contributor

scylla-operator-bot Bot commented Oct 11, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mfreeman451
Once this PR has been reviewed and has the lgtm label, please assign tnozicka for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tnozicka
Copy link
Copy Markdown
Contributor

tnozicka commented Oct 11, 2024

/ok-to-test

Thanks for your contribution. Please format the commit message to imperative mood. (If this commit is applied it will ...)
E.g. Fix typo in helm docs

@scylla-operator-bot scylla-operator-bot Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 11, 2024
@tnozicka tnozicka added the kind/documentation Categorizes issue or PR as related to documentation. label Oct 11, 2024
@scylla-operator-bot scylla-operator-bot Bot removed the do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. label Oct 11, 2024
@tnozicka tnozicka added priority/backlog Higher priority than priority/awaiting-more-evidence. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Oct 11, 2024
@scylla-operator-bot scylla-operator-bot Bot removed the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Oct 11, 2024
@scylla-operator-bot
Copy link
Copy Markdown
Contributor

scylla-operator-bot Bot commented Nov 10, 2024

The Scylla Operator project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 30d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out

/lifecycle stale

@scylla-operator-bot scylla-operator-bot Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 10, 2024
@scylla-operator-bot scylla-operator-bot Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 25, 2024
@scylla-operator-bot
Copy link
Copy Markdown
Contributor

scylla-operator-bot Bot commented Nov 25, 2024

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@scylla-operator-bot
Copy link
Copy Markdown
Contributor

scylla-operator-bot Bot commented Dec 26, 2024

The Scylla Operator project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 30d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle rotten
  • Close this PR with /close
  • Offer to help out

/lifecycle rotten

@scylla-operator-bot scylla-operator-bot Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 26, 2024
@scylla-operator-bot
Copy link
Copy Markdown
Contributor

scylla-operator-bot Bot commented Jan 8, 2025

@mfreeman451: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gke-multi-datacenter-parallel 6415e32 link true /test e2e-gke-multi-datacenter-parallel

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@scylla-operator-bot
Copy link
Copy Markdown
Contributor

scylla-operator-bot Bot commented Feb 8, 2025

The Scylla Operator project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 30d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Reopen this PR with /reopen
  • Mark this PR as fresh with /remove-lifecycle rotten
  • Offer to help out

/close

@scylla-operator-bot
Copy link
Copy Markdown
Contributor

scylla-operator-bot Bot commented Feb 8, 2025

@scylla-operator-bot[bot]: Closed this PR.

Details

In response to this:

The Scylla Operator project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 30d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Reopen this PR with /reopen
  • Mark this PR as fresh with /remove-lifecycle rotten
  • Offer to help out

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@rzetelskik rzetelskik Awaiting requested review from rzetelskik

@tnozicka tnozicka Awaiting requested review from tnozicka

Assignees

No one assigned

Labels

do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. kind/documentation Categorizes issue or PR as related to documentation. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. priority/backlog Higher priority than priority/awaiting-more-evidence. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@mfreeman451 @tnozicka